Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference
470-tree-1
name
1662
tree-preservation-order

undefined

470-tpo-1
uprn
address-text
point
POINT (-1.023490 50.882674)
geometry
MULTIPOLYGON (((-1.023447 50.882670,-1.023449 50.882678,-1.023455 50.882686,-1.023464 50.882692,-1.023476 50.882696,-1.023489 50.882697,-1.023503 50.882696,-1.023515 50.882692,-1.023524 50.882686,-1.023530 50.882679,-1.023533 50.882670,-1.023531 50.882662,-1.023525 50.882654,-1.023516 50.882648,-1.023504 50.882644,-1.023491 50.882643,-1.023477 50.882644,-1.023465 50.882648,-1.023456 50.882654,-1.023450 50.882661,-1.023447 50.882670)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL